5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL COMPILE PROC


This subroutine compiles the specified Process Type/Name or Application.

Usage:

Description:

This subroutine compiles the specified Process Type/Name or Application. The first 2 parameters are required. If any required parameters are missing, the subroutine will CANCEL.

<application> is the application that contains the processes to be compiled (Required).

<version> is the version of the above application (Required).

<proc_type> is the process type to be compiled (Optional). If PASSed, this must be a valid Process Type, INPUT, OUTPUT, JOB, SUBROUTINE, etc. If not PASSed, then all processes in <application> will be compiled.

<proc_name> is the process name to be compiled (Optional). You can only PASS this if you also PASS the <proc_type>. If not PASSed, then all processes of type <proc_type> will be compiled.

This subroutine performs the same function as 'Create Executable Modules' in application design. Only Em's that need to be rebuilt will be compiled. A message will appear in the status area when Appx is actually compiling an Em.

If .UTIL COMPILE PROC is blank, it means the compiler was successfully invoked, it does not mean that every process compiled successfully. You must check the --- PCERR file to see which processes had errors, if any. The --- PCERR ERR NO field can be used to read --- MESSAGE to get a readable error message:

The --- PCERR STMT field will contain the problem statement, in printable form.

Application Design Manual                                         "Powered by Appx Software"

1175

©2006 By APPX Software, Inc. All Rights Reserved